Use an app token for triggering a release#2644
Conversation
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.
Comments skipped due to low confidence (1)
.github/workflows/post-release-mergeback.yml:166
- The new token generation step should be tested to ensure it works as expected. Consider adding a test workflow to validate the token creation process.
uses: actions/create-github-app-token@5d869da34e18e7287c1daad50e0b8ea0f506ce69
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
henrymercer
left a comment
henrymercer
left a comment
There was a problem hiding this comment.
The indentation doesn't look quite right, but otherwise this looks good!
We need to do this because using a default token will not recursively trigger a new workflow run.
aeisenberg
force-pushed
the
aeisenberg/use-app-token-for-release
branch
from
1a19005 to
9a8645d
Compare
|
Fixed the indentation. After merging, I will do a release to see if this fixes the problem. |
NlightNFotis
left a comment
NlightNFotis
left a comment
There was a problem hiding this comment.
Code-wise, this looks good.
The only question is whether the permissions are adequate for performing the release, but I guess we won't know until we try it.
I believe so. We need |
3 participants
We need to do this because using a default token will not recursively trigger a new workflow run.
The only way to test this is to merge to main and do a release.
Merge / deployment checklist